Expand repo taxonomy to 9 types and add public repository policy#14
Expand repo taxonomy to 9 types and add public repository policy#14Ethan-Arrowood wants to merge 4 commits into
Conversation
Taxonomy: replace the catch-all `core` type with `product`, `plugin`, `application`, `library`, and `meta`, keeping `template`, `example`, `guide`, and `snapshot`. Add a classification decision tree, per-type sections with upgrade/testing guidance, and link Plugin/Application to the Harper component reference docs. Policy: add docs/repository-policy.md — the human- and agent-readable reference for managing active public repos (ownership, taxonomy topic, required meta docs, declared Harper version, testing/upgrades) plus a Public Archived section. Cross-link the two docs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the Harper Public Repository Taxonomy and introduces a new Harper Public Repository Policy to establish clear maintenance contracts for public repositories. The review feedback identifies a minor grammatical omission, a logical gap in the classification decision tree for repositories that do not contain a config.yaml file, and a broken reference in the policy document pointing to a deleted section of the taxonomy.
Match the repository-policy.md naming and update cross-links. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
kriszyp
left a comment
kriszyp
left a comment
There was a problem hiding this comment.
This looks good to me. I think one of the more important aspects of this is that it should be a stronger gate to creating new templates, examples, plugins, etc.; if there isn't a commitment to maintenance, than it can't be defined as one of those.
2 participants
Summary
Iterates the repo taxonomy from the initial 5-type model into a 9-type model, and adds a companion public repository policy document.
Taxonomy (
docs/repo-taxonomy.md)coretype with five sharper types:product,plugin,application,library, andmeta— keepingtemplate,example,guide, andsnapshot.plugin/application/librarytrack Harper closely;productis independently versioned;metais public-but-not-a-product;snapshotis frozen.Policy (
docs/repository-policy.md, new)The human- and agent-readable reference for managing active, public repos. Baseline commitments:
LICENSE,README)dependencies/peerDependenciesorengines(semver)Plus a Public Archived section (archived ≠ deleted, when to archive, keep-public vs. move-internal, the required archive README note, and when deletion is warranted).
The two docs cross-link each other. Internal/private repos are explicitly out of scope (separate policy to come).
🤖 Generated with Claude Code